NOTE -- 2021 version of GLFPE for Windows 28 Nov 2021 GLF -------------------------------------------------------------------------------- The GLF Programming Environment (GLFPE) for Windows is intended to provide the functionality to allow an interested user to edit, compile, and run a variety of C or C++ programs (and a little FORTRAN. COBOL, and Python on the side) in a manner which is compatible with the methidology used by its author, Gary L. Flispart (GLF). Similar toolsets have been successfully ported to multiple platforms, including Windows, Debian Linux 64 bit and 32 bit, and Raspberry Pi OS. Each platform can host and compile any of the more than 700 program projects in the GLFPE sample source code suite. As of this writing, all components of GLFPE so far included in the iterative installation ZIPs have been tested functional on both Windows 10 and Windows XP using the a copy of the original 2018 source code tree (\prg\win\orw630 converted to \prg\win\dev920). Project files have been edited as needed to reflect the current compiler, binary and library locations. Some wxWidgets projects have been altered to specify -std=gnu-c++98 when compiling C++ code, to allow successful builds using the newer GCC and G++ 9.2.0. The newer C++ standards (2011 and 2014) seem to break the old wxWidgets 2.8.12 source, but that trick worked for the Linux builds, too. The PDCurses 3.4 library is old but stable, and has been compiled with the newer GCC. Similarly, the wxWidgets library is also old but stable, and compiled with the newer GCC. The GMP library is included with MinGW32 and is of recent vintage. All other GLFPE library support (images, sound, SDL, Allegro, FLTK, etc.) have been copied as binaries from the prior compilations performed in 2018 using GCC 6.3.0. These are fully compatible with existing (old) GLFPE sample source, and all programs which compiled and ran before do so now. The GLFPE sample source tree from the default Linux platform has been successfully updated to the current 2021 GLF tree, except for the OpenCV Tutorials, which for this 2021 Windows toolchain release remain as OpenCV version 2.4, due to the impracticality of adapting newer versions of OpenCV to the MinGW32 compiler. The planned future release in 2022 of the successor to this toolset will use a different compiler, which will no longer be runnable on Windows XP, though it should still be able to produce code which can run on the older platform. This 2021 release is the last planned release to support Windows XP and later OS. NOTE on malware scans and potential false positives --------------------------------------------------- In order to install the GLFPE for Windows toolchain, it is necessary for a user to extract the files from a ZIP file or files produced and distriburted by GLF. It is pretty much mandatory to run antivirus software on any Windows computer connected to the internet. It is always possible that during the unpacking and copying of files, the user's installed AV will detect what it believes to be malware, bloking the installation and generating anxiety and mistrust. A longstanding problem for distribution of compiler tools as in the GLFPE which encapsulate a large number of programs and data is that malware may creep in, but also that malware may be falsely detected by AV. Since the original sources of the various programs on the internet are generally trusted by many (thousands to millions), it is always possible that malware can creep in unexpectedly either when downloading original files or when repackaging them into an installable set. Over many years, GLF has experienced several instances of temporary false positive detection by several AV engines, on bth compiler tool executables and on binaries produced by those tools. AV signatures are sometimes aggressive in identification of a suspicious string of bytes, and sometimes slow in responding to authoritative retraction of such flags. Compilers necessarily DO things that change the file structure on computers, and so are both targets for malware distribution and for detection of same. All such incidents of AV (false) detection within the GLFPE installed toolsets known to GLF in personal experience have eventually been cleared by the various AV engines as harmless. GLF cannot guarantee that no such incursion has taken place in the archives produced to distribute GLFPE, but GLF has recently tested the installed set of tools using Avast Antivirus, and no malware has been detected in the set. One problem which still might raise its head can be caused by an old, unupdated antivirus scanner still inflicted with false positives in its signature files. Such a problem showed up when testing the current BETA release of the GLFPE Windows toolset on an old Windows XP machine. The machine has not been connected to the internet in many tears, and is retained by GLF for such testing. However, that machine also had an old, still running, copy of Avira Antivirus, and while installing the toolset from ZIP files, two files were flagged and blocked. The signature files in this case were ancient and obsolete, and likely caused false positive detections, which might have been corrected by the vendor had updates continued over the intervening years. It is difficult to track the changes in signatures for AV vendors, and they rarely publish notices about fablse positives. They just quietly fix their files in response to complaints, if there are enough of them. It was not possible to continue installation without disablng the AV. Before doing so, GLF used a current version of Avast Antivirus to scan all files in the original tree from which the ZIP was compiled, and found no malware. Also, the two files identified were uploaded to the website "VirusTotal" to scan with a large number of alternate engines. One file showed no detections by 30 or so engines, and the other showed 1 detection in the group, and not by any of the major AV vendors in the list. If a file is much newer than the AV engine, and few or no current scanners detect malware, that is a pretty good sign of a false positive signature by the few that do. It is not possible to upload all the files to the multiscanner of VirusTotal, but it is reasonable to rely on the very reliable reputatation of a major AV vendor such as Avast. If it doesn't see malware, there probably isn't any.